A minimum of two Oracle redo log groups/files must be defined and configured to be stored on separate, archived physical disks or archived directories on a RAID device.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-53969	O112-BP-021600	SV-68209r1_rule		Medium

Description
The Oracle redo log files store the detailed information on changes made to the database. This information is critical to database recovery in case of a database failure.

STIG	Date
Oracle Database 11.2g Security Technical Implementation Guide	2017-04-05

Details

Check Text ( C-54759r1_chk )
From SQLPlus: select count() from V$LOG; If the value of the count returned is less than 2, this is a Finding. From SQLPlus: select count() from V$LOG where members > 1; If the value of the count returned is less than 2 and a RAID storage device is not being used, this is a Finding.

Fix Text (F-58809r1_fix)
To define additional redo log file groups: From SQLPlus (Example): alter database add logfile group 2 ('diska:log2.log', 'diskb:log2.log') size 50K; To add additional redo log file [members] to an existing redo log file group: From SQLPlus (Example): alter database add logfile member 'diskc:log2.log' to group 2; Replace diska, diskb, diskc with valid, different disk drive specifications. Replace log#.log file with valid or custom names for the log files.

Fix Text (F-58809r1_fix)

To define additional redo log file groups:

From SQL*Plus (Example):

alter database add logfile group 2
('diska:log2.log', 'diskb:log2.log') size 50K;

To add additional redo log file [members] to an existing redo log file group:

From SQL*Plus (Example):

alter database add logfile member 'diskc:log2.log' to group 2;

Replace diska, diskb, diskc with valid, different disk drive specifications.

Replace log#.log file with valid or custom names for the log files.